chore: sync Go client with Apify OpenAPI spec v2-2026-06-30T091455Z - #10
Merged
Conversation
Version-only sync from v2-2026-06-29T142258Z. An independent operation- and parameter-level audit of the new spec (131 paths / 231 operations), with the apify-client-js reference as the in-scope parity authority, found no change to the in-scope API surface. Bumps the version constants to 0.4.3 (patch) and fixes documentation/changelog consistency flagged by review. - version.go: API_SPEC_VERSION -> v2-2026-06-30T091455Z; CLIENT_VERSION -> 0.4.3 - CHANGELOG.md: [0.4.3] entry (API_SPEC_VERSION, CLIENT_VERSION, README sync) - README.md: Versioning section spec version synced to version.go - docs/actors.md: document nil waitSecs behavior for Call
…rement The updated client requirements mandate that each PR's CHANGELOG entry contain only a short list of the changes in that PR, with no narrative, no process text, no out-of-scope/not-implemented notes, and no sibling-client references. Rewrote the [0.4.3] entry accordingly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Synchronizes the Go client with the latest Apify OpenAPI specification,
info.versionv2-2026-06-30T091455Z(previouslyv2-2026-06-29T142258Z).An independent operation- and parameter-level audit of the new spec (131 paths / 231 operations),
using the
apify-client-jsreferenceclient as the parity authority for which endpoints are in scope, found no change to the in-scope
API surface. A cross-check of all 71 distinct spec query parameters against the source confirmed
every in-scope parameter remains exposed (the only absent ones belong solely to out-of-scope
endpoints). This is therefore a version-only sync — a SemVer patch release (
0.4.2→0.4.3).Changes
version.go:API_SPEC_VERSION→v2-2026-06-30T091455Z,CLIENT_VERSION0.4.2→0.4.3CHANGELOG.md: new[0.4.3]entryREADME.md: "Versioning" section spec version synced toversion.go(the prior release'ssync-checklist step, restored)
docs/actors.md: document the nil-waitSecsbehaviour ofCallVerification
gofmt -l .— clean;go vet ./...— clean;go build ./...— cleango test .(offline) — okgo test ./tests/ -p 1 -parallel 4 -skip '^(TestExample|TestDocSnippets)'(live API) — ok, 0 failuresgo test ./tests/ -run '^(TestExample|TestDocSnippets)'(examples + doc snippets) — ok, 0 failuresGenerated by Claude Code